Skip to main content

Home/ Web Accessibility/ Group items tagged assistive technology

Rss Feed Group items tagged

Sandra Earl

E-Access Blog » Blog Archive » Organisation in the Spotlight - W3C: Global St... - 0 views

  • One major new piece of work undertaken by WAI is the EC-funded WAI-AGE Project (http://www.w3.org/WAI/WAI-AGE/), a look at the implications of an ageing population for web access, given the older people are more likely to have disabilities and may also be less familiar with new technologies. “Demographics worldwide are dramatically changing at the moment,” says Andrew Arch, who works with Abou-Zahra on WAI-AGE. “The proportions of older to younger people are changing as well as the numbers. We’re living longer, and we haven’t got the support behind us. “Lots of things have got to change in governments and organisations - with an ageing workforce, you have to keep learning to stay accessible.”
  • The WAI-AGE project is partly aimed at finding out whether there are any significant new pieces of work needed to ensure web accessibility for an older population, Arch says. “We’ve looked at what research and user observation has gone on over the decade. There is a pretty big overlap between older people and others with disabilities - sight starts to decline, motor dexterity - and individually these overlap. But with older people there is often a lack of recognition that there is a disability there. For example some people might just say they can’t remember so well, rather than that they have a cognitive impairment. Or people won’t see failing eye-sight as a disability, it’s just ‘part of growing old’. But they are disabilities, and often multiple disabilities.”
  • Having gained a grasp of current research the project returned to guidelines such as WCAG 2.0 to see if any changes might be needed. “A large proportion of the needs of older people are met by the new guidelines, but other things might need to feed into the guidance we will issue on implementing the guidelines, for example guidance on how people prepare content for older people.,” said Arch. “Many older people have not grown up with computers, and may not realise their capabilities, for example that you can magnify text in your browser.”
  • ...4 more annotations...
  • This argument is a development of the age-old mantra from the accessibility sector that people with disabilities want to use the web in the same way as everybody else - “it is a human right recognised by the UN,” says Abou-Zahra. But he recognizes that businesses in particular will also  be interested in the additional business benefits, especially in the current financial climate.
  • “With commercial organisations the return on investment is often an important argument. Well, a few years ago, companies might have said ‘how many older people are online?’ but with demographics changing they know the answer. And with the current surge in mobile phone use there is another incentive, since accessible sites work better on mobile phones.”
  • Another change of style will be a greater separation between the core guidelines and references to specific technologies such as Javascript or browser types, Abou-Zahra says.
  • “WCAG 1.0 was too  technology-specific. Back then HTML was more dominant, and there was less use of multimedia, but today we have a flurry of technologies such as Ajax, so the first lesson we learned is don’t write for a specific technology. Also, in the days of WCAG 1.0 we had to exclude Javascript because it was not sufficiently standardised and  assistive technology could not handle it consistently, but now that has largely changed so you need to include it, to look at how any technology should be accessible. The requirements - such as tagging images with text - needs to apply to any technology you are using.
Vernon Fowler

HTML5 accessibility - 0 views

  •  
    This site is a resource to provide information about which HTML5 user interface features are accessibility supported in browsers, making them usable by people who rely upon assistive technology (AT) to use the web.
Vernon Fowler

A List Apart: Articles: Now You See Me - 0 views

  • visibility: hidden; Element is hidden from view, but is not removed from the normal flow (i.e., it still takes up the space it normally would) Content is ignored by screen readers display: none; Element is removed from the normal flow and hidden; the space it occupied is collapsed Content is ignored by screen readers height: 0; width: 0; overflow: hidden; Element is collapsed and contents are hidden Content is ignored by screen readers
  • if you want to ensure users have access to content (even if it isn’t displayed visually in the current interface), the final option (positioning content offscreen) is really the way to go.
  • Screen readers have access to the content
  • ...6 more annotations...
  • position: absolute; left: -999em;
  • but links may “focus” oddly and negative indent may not prove long enough to fully hide content
  • limited to text and inline elements
  • Content is removed from the normal flow and shifted off the left-hand edge; the space it occupied is collapsed
    • Vernon Fowler
       
      This is usually my desired effect.
  • If you don’t want your hidden content to be read by a screen reader, those defaults may work for you
  • how profoundly your choice of hiding mechanism can influence the accessibility of your content to assistive technologies like screen readers
Vernon Fowler

Inclusively Hidden | scottohara.me - 0 views

  • sometimes content is for decorative purposes only, and it would be optimal to not announce this content to assistive technology.
  • don’t use aria-hidden on focusable content
  • Purposefully Hidden from Assistive Technology
  • ...1 more annotation...
  • using aria-hidden to hide content specifically from screen readers
  •  
    There are various techniques to visually hide content in our web interfaces, but are you aware of the different effects they have on the accessibility of that content? While it would be nice if there was a single, native, solution for hiding content, there are contextual benefits to the various techniques at our disposal. Since there have been many articles already written about these techniques, over the many years they've been in use, the focus of this article will be to highlight the ones that are most appropriate for modern web development. We won't just look at the code behind each of these techniques, instead we'll focus on why each technique has its place, using practical examples to demonstrate their purposes. But before we talk about how to hide content we should ask ourselves a question… Why are we hiding content?
Sandra Earl

Captivate Accessibility Hints | SSB BART Group - 0 views

  • Captivate has a number of accessibility features in version 3 and 4 although there are some issues that Adobe is working on.
  • Ensure that the “enable accessibility” checkbox is checked under the File > Publish settings in order for accessibility to be exposed to assistive technologies.
  • Slide Accessibility Text Each slide can contain accessibility text. This can be added by going to the slide properties, activating the Accessibility button and entering text in the text field.
  • ...6 more annotations...
  • Closed Captioning Closed captioning can be added to all audio files. From the record audio dialog, closed caption text can be added under the Caption tab. The playback bar contains a CC button which allows the closed captioning to be displayed or hidden.
  • Button Accessibility Text buttons can be made accessible. The text that appears on-screen becomes the button’s accessible name. To make the buttons keyboard accessible, the “Set Keystroke: Select Keys” button should be used and the keystroke of “enter” should be set in the object’s properties dialog. Other shortcuts can be assigned but enter/space will then not work to activate the button after tabbing to it. The keystroke of “enter” can be assigned to multiple buttons and the button with focus will be activated when Enter is pressed.
  • Audio recordings can be associated with click boxes and thus authors can associate descriptive text to be announced when a shortcut keystroke is pressed to assist users with visual impairments.
  • Text from PowerPoint Much of the text from PowerPoint will come through as text in Microsoft Active Accessibility (MSAA) and will be exposed to users of screen readers. Currently there isn’t a method to change the order or edit this text.
  • Quiz Questions There is some accessibility support for quiz questions. Simple types of questions such as true and false and multiple choice provide accessible names for the radio buttons and the text of the question appears as text in the accessible MSAA structure and is exposed to screen readers.
  • Accessibility Differences Between Captivate 3 and 4 The text in the “text caption” object does not show up as accessible text in Captivate 3 but does in Captivate 4. In addition, it is not possible to set accessible text for specific images in Captivate 3 but it is possible in Captivate 4.
Vernon Fowler

Responsive Design is Too Responsive? - 0 views

  • When you use browser zoom in Webkit browsers (Chrome and Safari), all elements on the page increase in size and start overlapping content. This is because WebKit browsers zoom to make the content bigger but the width of the browser remains unaffected, which means it doesn’t trigger responsive style sheet elements or address layout issues.
  • This is an accessibility issue as users with vision deficiencies use browser zoom to navigate websites. If they use Google Chrome they will have a lot of issues accessing content.
Sandra Earl

E-Access Blog » Blog Archive » Global Online Accessibility Resource Set For 2... - 0 views

  • An online resource of open source, royalty-free assistive technology tools, accessible and usable at any time and across the world, is to be launched next year by a consortium of more than 30 US and European IT and disability organisations and leaders, the European Commission e-Inclusion conference heard this month.
Vernon Fowler

WCAG 2.1 is Coming-and Here's What You Should Know Right Now - Siteimprove - 0 views

  • Expect the new WCAG standards to emphasize a mobile experience that matches what users might expect from a traditional browsing session. This will likely include making your site’s touch screen functions more compatible with assistive technology. 
  • The new standards are expected to raise that level to 400% to help users with low vision navigate sites more smoothly.
  • WCAG 2.1 will likely seek to place limits on where and when pop-ups and similar advertising can appear. 
  • ...1 more annotation...
  • For users with motor skill issues, clicking on incorrect links and buttons is a common problem. WCAG 2.1 will likely require improvements in navigation technology that makes it easier both to find the right link and to correct actions if the wrong link is clicked. 
  •  
    Considering how massively the online landscape has changed in the past decade, it's amazing that international standards for web accessibility haven't been updated since December of 2008. That's about to change. After soliciting and assessing recommendations from the public, the international Web Accessibility Initiative is set to announce version 2.1 of its Web Content Accessibility Guidelines in the middle of this year. As that update draws nearer, there are a few key changes website owners may want to start planning for. (Keep in mind that all WCAG 2.1 changes are tentative.)
Vernon Fowler

HTML5 Accessibility Chops: When to use an ARIA role | The Paciello Group Blog - 0 views

  • The situation for new HTML5 elements is different and likely to remain so for some time. It will be years before New HTML5 elements get robust accessibility support implemented across browsers and platforms. This is particularly so for non interactive elements such as the new HTML5 structural elements because  accessibility APIs in general do not have defined roles for many non interactive elements. In this case it is recommended to add the appropriate ARIA roles to elements that are meant to convey meaning but are effectively meaningless due to lack of implemented accessibility support. For example, adding role=navigation to a nav element fills the gaps in support for HTML5 semantics as ARIA  is more robustly  supported by most modern browsers and assistive technology:
  • <nav role=”navigation”>
  • Authors/developers can safely assume that any element that has been around since HTML 4.0 is already accessibility supported in browsers that support accessibility. So they do not need a default implicit role added.
Vernon Fowler

Accessible forms using WCAG 2.0 | Web Usability - 0 views

  • The label element is not used for the following because labels for these elements are provided via the value attribute
  • This technique inserts new content into the DOM immediately following the element that was activated to trigger the script. The triggering element must be a link or a button, and the script must be called from its onclick event. These elements are natively focusable, and their onclick event is device independent. Focus remains on the activated element and the new content, inserted after it, becomes the next thing in both the tab order and screen-reader reading order. Note that this technique works for synchronous updates. For asynchronous updates (sometimes called AJAX), an additional technique is needed to inform the assistive technology that the asynchronous content has been inserted.
Sandra Earl

BBC Internet Blog - 0 views

  • We considered a few approaches, but decided to grow our new widget out of Adobe Flex and Adobe AIR. This is firstly because these tools met our requirements to work cross-platform and deliver the desktop experience we wanted, and also because they linked up with in-house skills in the team which manages them, making them simpler to manage.
  • BBC Future Media & Technology's pilot widget application BBC LiveUpdate uses the Adobe AIR runtime, which is dependent on users downloading and installing a plugin to their desktop, but which unfortunately does not currently support screenreaders (or other software which relies on the Microsoft Active Accessibility layer for assistive technologies). We're working with Adobe to make tools built with AIR more accessible than current products wherever possible and are committed to delivering accessible services. As this is a beta product, there are also other limitations in how much we have been able to establish accessibility support in the following areas:Colour contrast cannot be alteredText size cannot be alteredLacks consistent alt textLacks Title attributesIs not entirely tabbable.
Sandra Earl

YUI Theater - Karo Caran and Victor Tsaran: "Introduction to Screen Magnifier... - 0 views

  • With the goal of better understanding how people interact with the Web via various types of Assistive Technology (AT) — and what that might mean for developers and designers — Karo Caran takes us on a 16 minute overview of screen magnification software (in this case ZoomText) and how it is used by partially-sighted users to interact with the Web. Karo shows you the basic toolkit and then applies those tools to some typical web sites to give you some perspective on how she uses magnification software while she browses the web.
Sandra Earl

E-Access Bulletin Live » Blog Archive » Disability Redefined As E-Learning 'M... - 0 views

  • An attempt to redefine or reframe the term ‘disability’, in the context of online learning as a mismatch between a learner’s needs and the education process delivered, is enshrined in a new international e-learning standard.
  • The standard says it views disability as “a consequence of a mismatch between the learner’s needs (or preferences) and the education or learning experience delivered. “For example, an individual who is blind is not disabled when the lesson is delivered in audio. However, an individual who does not have the necessary background knowledge to understand the lesson, or who is listening to the lesson in a noisy environment, is disabled. “Thus, the needs and preferences of a user may arise from the user’s context or environment, the technical requirements of the user’s device, the tools available (e.g. assistive technologies such as Braille devices, voice recognition systems, alternative keyboards, etc.), the user’s background, or a disability in the traditional sense. “Given this reframing of the meaning of “disability”, a learning environment is deemed as “accessible” when learner needs can be addressed or matched.”
1 - 20 of 23 Next ›
Showing 20 items per page